XR Rel-18

 RAN1#109-e

9.11   Study on XR enhancements for NR

Please refer to RP-220285 for detailed scope of the SI.

 

R1-2205053        Work plan for Rel-18 SI on XR enhancements for NR         Qualcomm Incorporated

 

R1-2204673        TR 38.835 Skeleton for Study on XR enhancements for NR Rapporteur (Nokia)

[109-e-R18-XR-01] – Margarita (Nokia)

Email discussion and approval of TR skeleton for Rel-18 SI on XR enhancements for NR by May 13

R1-2205329        TR 38.835 Skeleton for Study on XR enhancements for NR Rapporteur (Nokia)

Decision: As per email decision posted on May 15th,

Agreement

The TR skeleton for TR 38.835 Study on XR enhancements for NR (R1-2205329) is endorsed as v0.0.1 from RAN1 perspective. Send LS to RAN2 to convey this agreement.

 

R1-2205419        [Draft] LS on draft TR 38.835 skeleton     Nokia

Decision: As per email decision posted on May 16th, the draft LS is endorsed. Final LS is approved in R1-2205443.

9.11.1     XR specific power saving techniques

R1-2203131        Discussion on XR-specific power saving techniques              Huawei, HiSilicon

Proposal 1: Further study power saving techniques to address the following XR-specific issues:

-          Non-integer periodicity

-          Jitter

Proposal 2: When studying the potential enhancements to address XR-specific issues, the following general principles are considered

-          Principle 1: The solutions should be forward compatible, e.g., applicable to potential new frame rate in the future.

-          Principle 2: Solution(s) that can address multiple or all the identified issues are more preferred.

Proposal 3: Further study the following directions for C-DRX and PDCCH monitoring enhancements to address the non-integer periodicity issue:

-          Adjusting the start offset of DRX OnDuration and/or the start offset of PDCCH monitoring

-          Adjusting the periodicity, e.g. configuring a cycle pattern

-          Multiple C-DRX configurations

Proposal 4: Further study the following mechanisms to allow skipping unnecessary PDCCH monitoring caused by jitter:

-          Configuring a PDCCH monitoring pattern within DRX OnDuration or Search Space duration to match jitter distribution;

-          Skipping unnecessary PDCCH monitoring once the XR frame is received correctly;

-          UE monitors PDCCH sparsely before the data arrival and monitors PDCCH densely once the data arrives, e.g., implicit SSSG switching based on data arrival.

Decision: The document is noted.

 

R1-2203348         Discussion on XR specific power saving techniques   Spreadtrum Communications

R1-2203484         UE Power saving techniques for XR              CATT

R1-2203585         Discussion on XR specific power saving enhancements            vivo

R1-2203606         Discussion on XR specific power saving techniques   ZTE, Sanechips

R1-2203638         Discussion on power saving enhancements for XR     Ericsson

R1-2203666         Discussion on XR enhancement for NR         China Telecom

R1-2203744         Considerations on power saving techniques for XR    Sony

R1-2203927         Considerations on XR-specific Power Savings            Samsung

R1-2203940         Discussion on XR specific power saving techniques   NEC

R1-2204028         Discussion on XR specific power saving techniques   OPPO

R1-2204123         Discussion on XR specific power saving enhancements            InterDigital, Inc.

R1-2204177         XR specific power saving techniques            TCL Communication Ltd.

R1-2204264         Views on XR specific power saving techniques          Apple

R1-2204326         Discussion on XR-specific power saving techniques  CMCC

R1-2204400         Discussion on XR specific power saving techniques   NTT DOCOMO, INC.

R1-2204414         XR-specific power saving techniques            Lenovo

R1-2204444         Discussion on XR specific power saving techniques   ITRI

R1-2204633         Discussion on XR-specific power saving techniques  LG Electronics

R1-2204655         Discussion on power saving techniques for XR           ETRI

R1-2204674         Discussion on XR-specific power saving enhancements            Nokia, Nokia Shanghai Bell

R1-2204698         On XR specific power saving techniques      MediaTek Inc.

R1-2204818         Discussion on power saving enhancements for XR applications              Intel Corporation

R1-2205176         Power saving techniques for XR     Qualcomm Incorporated   (rev of R1-2205054)

 

[109-e-R18-XR-02] – Huilin (Qualcomm)

Email discussion on XR power saving by May 20

-        Check points: May 13, May 20

R1-2205055        Moderator Summary#1 on XR specific power saving techniques      Qualcomm Incorporated

From May 13th GTW session

Agreement:

Rel-17 evaluation methodology for XR power saving captured in TR 38.838 is used as the baseline evaluation methodology for UE power evaluation of Rel-18 SI on XR enhancements.

 

Agreement:

Companies are encouraged to compare performance of the following Rel-15/16/17 features with the proposed enhancements for Rel-18 XR power saving evaluations. Power saving gain is calculated w.r.t. the AlwaysOn baseline.

·        Rel-15/16 CDRX including long DRX cycle, short DRX cycle and DRX command MAC CE and DCP

·        Rel-17 PDCCH adaptation including PDCCH skipping and SSSG switching

Note: up to companies to report the configuration of the Rel-15/16/17 features

 

 

R1-2205410         Moderator Summary#2 on XR specific power saving techniques            Moderator (Qualcomm)

R1-2205411        Moderator Summary#3 on XR specific power saving techniques      Moderator (Qualcomm)

From May 19th GTW session

Agreement:

For power saving study of Rel-18 XR SI, CDRX enhancements to evaluate in this study item are to be selected from the following:

·        High priority Issue 1-1: Alignment between CDRX and XR traffic for resolving the mismatch between CDRX cycle and XR traffic periodicity for each flow

·        High priority Issue 1-2: C-DRX enhancements to handle jitter

·        Medium priority Issue 1-3: CDRX enhancements for multiple XR traffic flows [Note 2]

·        Low priority Issue 1-4: CDRX enhancements to adjust to variable burst sizes and frame rate

o   Note: Some companies think the adjustment for variable burst sizes can be realized by existing spec already

·        Low priority Issue 1-5: low latency handling

·        Low priority Issue 1-6: SFN wraparound mismatch (if handled in RAN1)

FFS: how the solutions or the combination of the solutions can handle all the identified issues.

Note 1: Other considerations are not precluded

Note 2: It can also be adopted for addressing issue 1-1

Note 3: Companies are encouraged to clarify or provide more details of the proposed solutions, for addressing concerns from the group.

Additional details can be found in R1-2205411.

 

Agreement:

For power saving study of Rel-18 XR SI, PDCCH monitoring enhancements to evaluate in this study item are to be selected from the following

·        Low priority Issue 2-1: Alignment between PDCCH monitoring and XR traffic to resolve the mismatch between PDCCH monitoring periodicity and XR traffic periodicity.

o   Note: some companies think Rel-17 PDCCH monitoring adaptation can solve issue 2-1 or achieve similar intended outcome

o   Note: Solutions proposed for Issue 2-1 and those proposed for Issue 1-1 are motivated by the same issue, namely non-integer XR traffic periodicity. It is to be studied how they compare in in terms of power saving gain and capacity, (a) solutions proposed for Issue 1-1; (b) solutions proposed for Issue 2-1.

·        Low priority Issue 2-2: XR-dedicated PDCCH monitoring window to supplement CDRX for multi-flow traffic.

o   Note: some companies think Rel-17 PDCCH monitoring adaptation can solve issue 2-2 or achieve similar intended outcome

o   Note: Solutions proposed for Issue 2-2 and those proposed for Issue 1-3 are motivated by the same issue, namely multiple XR traffic flows. It is to be studied how they compare in in terms of power saving gain and capacity, (a) solutions proposed for Issue 1-3; (b) solutions proposed for Issue 2-2.

·        High priority Issue 2-3: Enhancements to Rel-17 PDCCH monitoring adaptation.

o   Note: Discussion on some enhancements may depend on the outcome of Rel-17 PDCCH monitoring adaptation maintenance

o   Note: The study on enhancement to R17 PDCCH monitoring adaptation should focus on the techniques that are used for addressing XR-specific issues, e.g., jitter

Note 1: Other considerations are not precluded

Note 2: Companies are encouraged to clarify or provide more details of the proposed solutions, for addressing concerns from the group.

 

Agreement:

For Rel-18 XR power saving enhancements, RAN1 further discusses by RAN1 #110 whether the issues below are to be addressed, and if so, which solutions should be selected for evaluation in this study item. These issues are low priority.

·        Issue 3-1: Misaligned UE transmission and reception.

·        Issue 3-2: Power saving by XR-aware scheduling.

o   Note 1b: XR SI objective has XR-awareness in RAN listed as a specific topic of RAN2 study

·        Issue 3-3: Unnecessary data transmission in allocated resources.

Note 1: Rel-18 XR SI objective only has CDRX enhancements and PDCCH monitoring enhancements explicitly listed as focus of RAN1 study

Note 2: Other considerations are not precluded

 

 

Decision: As per email decision posted on May 21st,

Conclusion

·        If no evaluation result is provided by any company for an issue, the issue is deprioritized. The issue and proposed enhancements for the issue will not be captured by RAN1 in TR 38.835.

·        If no evaluation result is provided by the proponent company for a proposed enhancement, the proposed enhancement is deprioritized. The proposed enhancement will not be captured by RAN1 in TR 38.835.

·        If multiple enhancement techniques are proposed for the same issue, there can be down selection among them for the consideration of candidate enhancement for study item recommendation by RAN1 at least based on performance (power saving and capacity), spec impact, signaling overhead and implementation complexity.

·        Companies are encouraged to provide detailed information for both the proposed enhancement and the existing power saving features used as the performance reference so that the evaluation results for both can be reproduced by other companies.

·        When using existing power saving features as the performance reference, companies are encouraged to configure the existing power saving features to achieve the best performance.

·        For evaluation of a proposed enhancement and evaluation of the existing power saving features as performance reference, companies are encouraged to provide the high load case (as defined in TR 38.838, Section A.2) results. Results for low load case can also be reported optionally.

 

R1-2205412        Final Moderator Summary on XR specific power saving techniques Moderator (Qualcomm)

 

 

[109-e-R18-XR-03] – Huilin (Qualcomm)

Email discussion on incoming LS (R1-2203219) on UE Power Saving for XR and Media Services by May 18

-        Email discussion to start on May 10

-        Relevant tdocs: R1-2203395, R1-2203487, R1-2203591, R1-2203592, R1-2204126, R1-2204926, R1-2204969

R1-2205413         Draft Reply LS on UE Power Saving for XR and Media Services           Moderator (Qualcomm)

Further revised in

R1-2205530        Draft Reply LS on UE Power Saving for XR and Media Services     Moderator (Qualcomm)

Decision from May 19th GTW session: The draft reply LS to SA2 is endorsed with the following correction

·        PDU set size (number of bits) or number of PDUs in a PDU set: RAN1’s understanding is that in comparison to the statistical information, real-time or dynamic information provided to gNB, if possible, can help scheduler make more efficient scheduling decision to enable UE power saving.

Final LS is approved in

R1-2205531        Reply LS on UE Power Saving for XR and Media Services RAN1, Qualcomm

MCC: Inform SA2/RAN2 that source still shows "Qualcomm [RAN WG1]", and should be corrected to "RAN1".

9.11.2     XR-specific capacity enhancements techniques

R1-2203065         XR Capacity Evaluation and Enhancements FUTUREWEI

R1-2203132         Discussion on XR-specific capacity  enhancements techniques Huawei, HiSilicon

R1-2203349         XR capacity consideration Spreadtrum Communications

R1-2203485         NR enhancement for XR capacity improvement          CATT

R1-2203586         Discussion on XR specific capacity enhancements     vivo

R1-2203607         Discussion on XR specific capacity enhancements techniques ZTE, Sanechips

R1-2203639         Discussion on capacity enhancements for XR              Ericsson

R1-2203689         Discussion on XR-specific capacity enhancements     NEC

R1-2203745         Considerations on capacity enhancements techniques for XR   Sony

R1-2203928         Considerations on XR Capacity Improvements           Samsung

R1-2203934         Discussion on XR specific capacity improvement techniques   Panasonic

R1-2204029         Discussion on XR specific capacity enhancements techniques OPPO

R1-2204124         Discussion on XR specific capacity enhancements     InterDigital, Inc.

R1-2204129         Discussion on XR specific capacity enhancements techniques III

R1-2204178         XR-specific capacity enhancements techniques           TCL Communication Ltd.

R1-2204265         Views on XR specific capacity enhancements techniques         Apple

R1-2204327         Discussion on XR-specific capacity enhancements techniques CMCC

R1-2204401         Discussion on XR specific capacity improvement enhancements            NTT DOCOMO, INC.

R1-2204415         XR-specific capacity enhancement techniques            Lenovo

R1-2204634         Discussion on XR-specific capacity enhancement techniques   LG Electronics

R1-2204656         Discussion on capacity enhancements techniques for XR          ETRI

R1-2204675         Discussion on XR-specific capacity enhancements     Nokia, Nokia Shanghai Bell

R1-2204699         On XR specific capacity improvement enhancements MediaTek Inc.

R1-2204759         Discussion on potential SPS enhancements for XR     CEWiT

R1-2204819         Discussion on capacity enhancements for XR applications       Intel Corporation

R1-2205056         Capacity enhancement techniques for XR     Qualcomm Incorporated

R1-2205072         Discussion on XR-specific capacity enhancements techniques FGI

 

//This one is to use NWM – please use RAN1-109-e-NWM-R18-XR-04 as the document name

[109-e-R18-XR-04] – Sorour (Ericsson)

Email discussion on XR capacity enhancement by May 20

-        Check points: May 13, May 20

R1-2205265        FL Summary#1 – Study on XR Specific Capacity Improvements     Moderator (Ericsson)

From May 13th GTW session

Agreement

Rel-17 evaluation methodology for XR capacity enhancement captured in TR 38.838 is used as the baseline evaluation methodology for XR capacity enhancement of Rel-18 SI on XR enhancements.

 

 

R1-2205266        FL Summary#2 – Study on XR Specific Capacity Improvements     Moderator (Ericsson)

From May 17th GTW session

Conclusion

Study of network coding for capacity enhancements during Rel-18 XR SI is down prioritized in RAN1.

 

 

R1-2205267        FL Summary#3 – Study on XR Specific Capacity Improvements     Moderator (Ericsson)

From May 19th GTW session

Agreement

·        For each candidate capacity enhancement technique for XR traffic, companies are encouraged to consider the following common principle for assessment of the candidate capacity enhancement technique:

o   Identify the XR-specific issue(s) that the enhancement technique is addressing

o   Identify the necessity of the enhancement technique to address the issues

o   Identify whether/how the enhancements provide benefit/performance capacity gain.

§  Consider at least feasibility, complexity, and system level performance evaluations in comparing the enhancement techniques. Power saving gains for a given enhancement technique can optionally be evaluated and considered in addition to these other aspects.

·        The baseline scheduling scheme when comparing the proposed capacity enhancements techniques is:

o   Dynamic scheduling and/or

o   Semi-persistent scheduling / Configured grant scheduling

§  Note: Companies are encouraged to additionally use DG scheduling as the baseline scheduling scheme when showing the capacity performance gain

 

 

Decision: As per email decision posted on May 20th,

Agreement

·        To support a candidate capacity enhancement technique for XR traffic, capacity performance gain by the technique as compared to baseline should be shown.

o   Capacity performance gain by the candidate technique as compared to baseline is a necessary condition to consider supporting the candidate technique.

Conclusion

Companies are encouraged to use the capacity Excel sheet attached with TR 38.838 in RP-213652 for recording the simulation results that are provided in their contributions.

 

Agreement

To study whether/how to support a candidate capacity enhancement technique for XR traffic based SPS/CG transmissions, companies are encouraged to consider the following studies:

·        Study enhancements related to multiple PDSCHs SPS transmission occasions in a period

·        Study enhancements related to multiple PUSCHs CG transmission occasions in a period

·        Study enhancements related to dynamic adaptation of SPS/CG parameters/configurations

·        Study enhancements related to non-integer periodicity for SPS/CG transmissions.

·        Note: Other studies are not precluded, as well as the combination of the above studies.

Follow the common principle for assessment of the candidate capacity enhancement technique.

 

Agreement

To study whether/how to support a candidate capacity enhancement technique for XR traffic based dynamic scheduling/grant transmissions, companies are encouraged to consider the following studies:

·        Study enhancements related to extending capability of single DCI scheduling multi-PDSCHs/PUSCHs for FR2-2 to FR1/FR2.

o   Note: whether and how to discuss enhancements may depend on the outcome of Rel-17 B52.6G UE feature discussion

·        Study enhancements related to HARQ-ACK and/or CBG transmissions for single DCI scheduling one or multi PDSCH(s).

·        Study enhancements related to allowing different configurations per PDSCH/PUSCH

·        Study enhancement related to scheduling request and/or BSR with the focus on L1 enhancements.

·        Note: Other studies are not precluded as well as the combination of the above studies.

Follow the common principle for assessment of the candidate capacity enhancement technique.

 

Conclusion

It is common understanding that studying of RAN2 proposed techniques for XR-awareness information to improve XR capacity can be studied in RAN1 upon request from RAN2.

 

Agreement

The following lists the candidate enhancements techniques for link adaptation to improve XR capacity that are proposed by companies RAN1#109-e.

·        At least the proponents are encouraged to justify the corresponding capacity benefits for XR traffic for considering potential study of these candidate enhancements techniques. 

o   Delta MCS

o   Soft HARQ-ACK feedback

o   Cooperative MIMO scheme via precoding technique - bi-directional training

o   Enhanced link adaptation for CBG-based transmission

o   CSI report enhancements to address the different BLER requirements of different XR flows

·        Follow the common principle for assessment of the candidate capacity enhancement technique.

 

Agreement

The following lists the candidate enhancements techniques based on measurement-gap link to improve XR capacity that are proposed by companies RAN1#109-e.

·        At least the proponents are encouraged to justify the corresponding capacity benefits for XR traffic for considering potential study of these candidate enhancements techniques. 

o   Dynamic L1 based MG activation/deactivation.

o   Reuse current R16/R17 RRM relaxation condition to allow scheduling in MG to transform the R16/R17 RRM power saving gain into capacity gain.

·        Follow the common principle for assessment of the candidate capacity enhancement technique.

 

Decision: As per email decision posted on May 21st,

Agreement

The following lists the candidate enhancements techniques to improve XR capacity that are proposed by companies RAN1#109-e.

·        At least the proponents are encouraged to justify the corresponding capacity benefits for XR traffic for considering potential study of these candidate enhancements techniques. 

o   Inter-UE/intra-UE multiplexing techniques, including e.g. finer granularity preemption indication

·        Follow the common principle for assessment of the candidate capacity enhancement technique.

 

R1-2205268         FL Summary#4 – Study on XR Specific Capacity Improvements           Moderator (Ericsson)

9.11.33     Other

R1-2203486         XR awareness scheduling and QoS control   CATT

R1-2203587         Discussion on other aspects for XR specific RAN enhancements            vivo

R1-2203608         Consideration about XR services    ZTE, Sanechips

R1-2203640         Discussion on XR-Awareness         Ericsson

R1-2204125         Discussion on XR-Awareness          InterDigital, Inc.

R1-2204266         Considerations on enhancements for XR       Apple

R1-2204635         Other aspects of XR enhancements for NR   LG Electronics

R1-2204676         Performance results of XR-related enhancements       Nokia, Nokia Shanghai Bell

R1-2204820         Views on XR specific RAN enhancement in QoS       III

R1-2204908         Discussion on XR-specific capacity and power issues based on SA2 outcome               Huawei, HiSilicon


 RAN1#110

9.11   Study on XR enhancements for NR

Please refer to RP-220285 for detailed scope of the SI.

 

[110-R18-XR] Email to be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc – Huilin (Qualcomm)

9.11.1     XR specific power saving techniques

R1-2205843         XR specific power saving techniques            TCL Communication Ltd.

R1-2205877         Discussion on XR-specific power saving techniques  Huawei, HiSilicon

R1-2205916         Discussion on power saving enhancements for XR     Ericsson

R1-2206007         Discussion on XR specific power saving techniques   Spreadtrum Communications

R1-2207860         Discussion on XR specific power saving enhancements            vivo       (rev of R1-2206061)

R1-2206105         Discussion on XR power saving techniques  III

R1-2206131         Considerations on power saving techniques for XR    Sony

R1-2206225         XR-specific power saving enhancements      Nokia, Nokia Shanghai Bell

R1-2206244         Discussion on XR specific power saving techniques   NEC

R1-2206328         Discussion on XR specific power saving techniques   OPPO

R1-2206384         UE Power saving techniques for XR              CATT

R1-2206436         Discussion on XR specific power saving techniques   Panasonic

R1-2206495         Power saving techniques for XR     Rakuten Mobile, Inc

R1-2206518         XR-specific power saving techniques            Lenovo

R1-2206601         Discussion on XR specific power saving techniques   Intel Corporation

R1-2206629         Discussions on techniques for XR Power Saving        Xiaomi

R1-2206702         Discussion on XR specific power saving enhancement for NR China Telecom

R1-2206846         Considerations on XR-specific Power Savings            Samsung

R1-2206931         Discussion on XR-specific power saving techniques  CMCC

R1-2206959         Discussion on power saving techniques for XR           ETRI

R1-2206965         On XR-specific power saving techniques      Google Inc.

R1-2207008         On XR specific power saving techniques      MediaTek Inc.

R1-2207042         Discussion on XR-specific power saving techniques  LG Electronics

R1-2207061         Evaluation on XR specific power saving techniques   ZTE, Sanechips

R1-2207253         Power saving techniques for XR     Qualcomm Incorporated

R1-2207263         Discussion on XR specific power saving techniques   InterDigital, Inc.

R1-2207351         XR specific power saving techniques            Apple

R1-2207426         Discussion on XR specific power saving techniques   NTT DOCOMO, INC.

 

R1-2207831        Moderator Summary#1 on XR specific power saving techniques      Moderator (Qualcomm Incorporated)

From Tuesday session

Conclusion

Conclude that “SFN wraparound mismatch” is a RAN2 issue. It can be left to RAN2 to address. RAN1 does not further study it.

 

Agreement

RAN1 recommends identifying a solution for enhancement of CDRX to align with XR traffic periodicity

 

Conclusion

RAN1 does not assume instantaneous jitter value for a frame is predictable for Rel-18 XR SI power saving study before further input is provided by SA.

 

 

R1-2207832        Moderator Summary#2 on XR specific power saving techniques      Moderator (Qualcomm Incorporated)

From Wed session

Conclusion

All the proposed PDCCH monitoring adaptation/reduction schemes including those for jitter handling need to be compared against the Rel-17 PDCCH monitoring adaptation which is to be used as performance reference.

 

Conclusion

UE transmission and reception alignment for Issue 3-1 is deprioritized for power saving in Rel-18 XR SI.

 

Conclusion

RAN1 does not assume dynamic switch of different XR video data rates or frame rates for Rel-18 XR power saving study before further input is provided by SA.

 

 

R1-2207833        Final Moderator Summary on XR specific power saving techniques Moderator (Qualcomm Incorporated)

For future meetings

·        Companies are encouraged to account the enhancement of CDRX to align with XR traffic periodicity in their further evaluations for XR power saving enhancements.

Conclusion:

·        Companies are requested to use the Excel sheet attached with TR 38.838 in RP-213652 for recording the simulation results that are provided in their contributions.

9.11.22     XR-specific capacity enhancements techniques

R1-2205751         XR Capacity Evaluation and Enhancements FUTUREWEI

R1-2205844         XR-specific capacity enhancements techniques           TCL Communication Ltd.

R1-2205878         Discussion on XR-specific capacity  enhancements techniques Huawei, HiSilicon

R1-2205917         Discussion on capacity enhancements for XR              Ericsson

R1-2206008         Discussion on XR specific capacity enhancements techniques Spreadtrum Communications

R1-2206132         Discussion on XR-specific capacity enhancements     Sony

R1-2206226         XR-specific capacity enhancements Nokia, Nokia Shanghai Bell

R1-2206329         Discussion on XR specific capacity enhancements techniques OPPO

R1-2206385         NR enhancement for XR capacity improvement          CATT

R1-2206475         Discussion on XR-specific capacity enhancements     NEC

R1-2206519         XR-specific capacity enhancement techniques            Lenovo

R1-2206602         Discussion on XR specific capacity enhancement techniques   Intel Corporation

R1-2206703         Discussion on XR specific capacity enhancement for NR          China Telecom

R1-2206847         Considerations on XR Capacity Improvements           Samsung

R1-2206932         Discussion on XR-specific capacity enhancements techniques CMCC

R1-2206960         Discussion on SPS and CG enhancements for XR capacity improvement               ETRI

R1-2206964         On XR-specific capacity enhancements techniques     Google Inc.

R1-2207009         On XR specific capacity improvement enhancements MediaTek Inc.

R1-2207043         Discussion on XR-specific capacity enhancement techniques   LG Electronics

R1-2207062         XR specific capacity enhancements ZTE, Sanechips

R1-2207077         Discussion on XR specific capacity enhancements     CEWiT

R1-2207095         Discussion on XR-specific capacity enhancements techniques FGI

R1-2207254         Capacity enhancement techniques for XR     Qualcomm Incorporated

R1-2207264         Discussion on XR-specific capacity enhancements techniques InterDigital, Inc.

R1-2207301         Discussion on XR-specific capacity improvements     Rakuten Mobile, Inc

R1-2207352         XR-specific capacity enhancements techniques           Apple

R1-2207427         Discussion on XR specific capacity improvement enhancements            NTT DOCOMO, INC.

R1-2207718         Discussion on XR specific capacity enhancements     vivo       (rev of R1-2206062)

 

R1-2207820        Moderator Summary#1 - Study on XR Specific Capacity Improvements               Moderator (Ericsson)

From Tuesday session

For further discussion this week

 

Agreement

RAN1 to make decision on the following in RAN1#110bis-e

·         Support single DCI scheduling multi-PDSCHs/PUSCHs which is currently supported for FR2-2 to other SCS in FR1/FR2

 

R1-2207821        Moderator Summary#2 - Study on XR Specific Capacity Improvements               Moderator (Ericsson)

From Wed session

Conclusion

There is no consensus in RAN1 on the benefits of enhancing SPS for the purpose of XR capacity enhancement

 

Agreement

When DG is used as the baseline scheme to study CG enhancements to improve XR capacity performance, for the performance evaluation scheduling, after SR is triggered, both BSR and UL data are can be transmitted using the UL grant after SR.

·        Companies are encouraged to provide the size of resources by the first UL grant after SR

Agreement

Whether/how to enhance BSR to improve capacity performance of XR traffic is within RAN2 scope and is not handled by RAN1.

·        Note that RAN1 can discuss techniques associated to enhanced BSR for CG and DG related studies RAN1.

·        Note that companies should indicate if and what BSR enhancement is assumed in their RAN1 proposals on CG and DG enhancements.

·        RAN1 can evaluate BSR enhancement to improve capacity performance

 

R1-2207822        Moderator Summary#3 - Study on XR Specific Capacity Improvements               Moderator (Ericsson)

Agreement

·        Deprioritize the study of CQI report for different BLER and/or different XR traffic to improve XR capacity performance.

Agreement

·        Deprioritize the study of intra/inter UE prioritization/multiplexing enhancements to improve XR capacity performance.

For future meetings:

Companies are requested to follow the following agreement and conclusion from RAN1#109-e. Check final FL summary for details.

·        Agreement

o   Rel-17 evaluation methodology for XR capacity enhancement captured in TR 38.838 is used as the baseline evaluation methodology for XR capacity enhancement of Rel-18 SI on XR enhancements.

·        Conclusion

o   Companies are encouraged to use the capacity Excel sheet attached with TR 38.838 in RP-213652  for recording the simulation results that are provided in their contributions.

 

Final summary in R1-2207823.


 RAN1#110-bis-e

9.10   Study on XR enhancements for NR

Please refer to RP-220285 for detailed scope of the SI.

9.10.1     XR specific power saving techniques

R1-2208952        UE Power saving techniques for XR           CATT

·        Proposal 1: Rel-17 PDCCH skipping adaptation should be enhanced to further reduce UE power consumption for XR services, e.g., non-scheduling DCI based PDCCH skipping.

·        Proposal 2: The extension of non-scheduling DCI format design could reuse the existing DCI format 1_1 in Rel-16 and not increase the size of DCI format with additional function in extending the PDCCH monitoring adaptation in PCell without introducing additional information field.

·        Proposal 3: The procedure of Rel-17 PDCCH skipping adaptation should be enhanced for delay sensitive XR service to avoid frequent skipping indication signal overhead, e.g., continuous skipping indication.

·        Proposal 4: The go-to-sleep indication should be enhanced to be jointly configured with PDCCH skipping indication in the XR-specific DCI for fast transition to the sleep state PDCCH skipping enhancement schemes.

·        Proposal 5: The adaptation indication for PDCCH skipping should be separately between XR and other indicated to avoid different services latency requirements.

·        Proposal 6: DRX enhancement for XR service should not affect other data services.

·        Proposal 7：The dynamic XR-dedicated PDCCH monitoring scheme customized the PDCCH monitoring control matching XR traffic generation and disassociate the PDCCH monitoring control by C-DRX is the feasible solution for C-DRX enhancement and does not have impact to the delay insensitive traffic arrival compared to the pre-configured non-uniform DRX cycles.

·        Proposal 8: The XR-dedicated PDCCH monitoring window should be supported for XR UE power saving due to the advantages that it doesn't affect other data services and is achievable.

·        Proposal 9:  The SPS enhancement with PDCCH skipping and go-to-sleep should be supported for XR UE power saving.

·        Proposal 10: The SPS enhancement that the pre-configured PDCCH monitoring window bundled with the reserved SPS resource for PDSCH would be provide the resource to meet the QoS requirement  of XR-specific traffic with obvious power saving gain.

·        Proposal 11: gNB awareness of UE playout buffer should be studied and supported for XR UE power saving.

·        Proposal 12: How to reduce UL power consumption caused by UL data transmission and UL control information feedback should be studied for potential power saving gain for XR service.

·        Proposal 13:  Alignment between PUSCH transmission and HARQ feedback should be studied and supported to reduce UL power consumption for XR UE, e.g., single DCI indicating UL transmission and DL transmission (including HARQ feedback for DL reception) simultaneously.

Decision: The document is noted.

 

R1-2208401         Discussion on power saving enhancements for XR     Ericsson

R1-2208420         Discussion on XR-specific power saving techniques  Huawei, HiSilicon

R1-2208566         Discussion on XR specific power saving techniques   Spreadtrum Communications

R1-2210273         Discussion on XR specific power saving enhancements            vivo       (rev of R1-2208660)

R1-2208781         Discussion on XR specific power saving enhancement for NR China Telecom

R1-2208862         Discussion on XR specific power saving techniques   OPPO

R1-2208999         XR specific power saving techniques            TCL Communication Ltd.

R1-2209069         Discussion on XR specific power saving techniques   Intel Corporation

R1-2209112         Considerations on XR specific power saving techniques           Sony

R1-2209128         XR-specific power saving techniques            Lenovo

R1-2209197         Evaluation on XR specific power saving techniques   ZTE, Sanechips

R1-2209263         Discussions on techniques for XR Power Saving        xiaomi

R1-2209354         Discussion on XR-specific power saving techniques  CMCC

R1-2209387         Discussion on XR specific power saving techniques   Panasonic

R1-2209410         Discussion on power saving techniques for XR           ETRI

R1-2209427         Discussion on XR specific power saving techniques   NEC

R1-2209456         Discussion on XR-specific power saving techniques  LG Electronics

R1-2209517         On XR specific power saving techniques      MediaTek Inc.

R1-2209535         XR-specific power saving enhancements      Nokia, Nokia Shanghai Bell

R1-2209597         XR specific power saving techniques            Apple

R1-2209619         Power saving techniques for XR     Rakuten Symphony

R1-2209636         On XR-specific power saving techniques      Google Inc.

R1-2209657         Discussion on XR specific power saving techniques   InterDigital, Inc.

R1-2209748         Considerations on Power Savings for XR      Samsung

R1-2209919         Discussion on XR specific power saving techniques   NTT DOCOMO, INC.

R1-2210002         Power saving techniques for XR     Qualcomm Incorporated

R1-2210084         Further Discussion on XR power saving       III

 

[110bis-e-R18-XR-01] – Huilin (Qualcomm)

Email discussion on XR power saving by October 19

-        Check points: October 14, October 19

R1-2210337        Moderator Summary#1 on XR specific power saving techniques      Moderator (Qualcomm Incorporated)

From Oct 11th GTW session

Agreement:

For enhancement of CDRX to align with XR traffic periodicity (i.e., Issue 1-1)

·        Prioritize semi-static solutions

o   FFS: Whether dynamic solutions will be also needed

 

R1-2210338        Moderator Summary#2 on XR specific power saving techniques      Moderator (Qualcomm Incorporated)

Presented in Oct 17th GTW session

 

 

Decision: As per email decision posted on Oct 20th,

Conclusion

“Retransmission-less CG for UL pose transmission (Item 3.3-5)” is a RAN2 issue, leave the discussion to RAN2, RAN1 does not further investigate the issue.

·       Note: how to capture evaluation results and findings will be separately discussed

Conclusion

RAN1 does not further study jitter handling by LP-WUS (Item 2.2-4) in Rel-18 XR SI

·       Note: how to capture evaluation results and findings will be separately discussed

Conclusion

In addition to the values for jitter in Table 5.1-2 in TR 38.838, the following statistical parameters for jitter can also be optionally evaluated in Rel-18 XR SI.

·       Note: This optional assumption is not applicable to the evaluation of 90 FPS and above

Parameter

unit

Optional value for evaluation

Mean

ms

0

STD

ms

5

Truncation range

ms

[-8, 8]

 

Conclusion

RAN1 deprioritizes DCP indicated SSSG switching (Item 3.3-4)

·       Note: how to capture evaluation results and findings will be separately discussed

 

Final summary in R1-2210339.

9.10.22     XR-specific capacity enhancements techniques

R1-2208377         XR Capacity Evaluation and Enhancements FUTUREWEI

R1-2208402         Discussion on capacity enhancements for XR              Ericsson

R1-2208421         Discussion on XR-specific capacity  enhancements techniques Huawei, HiSilicon

R1-2208661         Discussion on XR specific capacity enhancements     vivo

R1-2208782         Discussion on XR specific capacity enhancement for NR          China Telecom

R1-2208863         Discussion on XR specific capacity enhancements techniques OPPO

R1-2208953         NR enhancement for XR capacity improvement          CATT

R1-2209000         XR-specific capacity enhancements techniques           TCL Communication Ltd.

R1-2209070         Discussion on XR specific capacity enhancement techniques   Intel Corporation

R1-2209113         Considerations on XR-specific capacity enhancements             Sony

R1-2209129         XR-specific Capacity Enhancement Techniques         Lenovo

R1-2209156         Discussion on XR-specific capacity enhancements     NEC

R1-2209198         XR specific capacity enhancements ZTE, Sanechips

R1-2209355         Discussion on XR-specific capacity enhancements techniques CMCC

R1-2209388         Discussion on XR capacity enhancement techniques Panasonic

R1-2209457         Discussion on XR-specific capacity enhancement techniques   LG Electronics

R1-2209518         On XR specific capacity improvement enhancements MediaTek Inc.

R1-2209536         XR-specific capacity enhancements Nokia, Nokia Shanghai Bell

R1-2209598         XR-specific capacity enhancements techniques           Apple

R1-2209620         Discussion on XR-specific capacity improvements     Rakuten Symphony

R1-2209642         On XR-specific capacity enhancements techniques     Google Inc.

R1-2209658         Discussion on XR-specific capacity enhancements techniques InterDigital, Inc.

R1-2209749         Considerations on Capacity Improvements for XR      Samsung

R1-2209920         Discussion on XR specific capacity improvement enhancements            NTT DOCOMO, INC.

R1-2210003         Capacity enhancement techniques for XR     Qualcomm Incorporated

 

[110bis-e-R18-XR-02] – Sorour (Ericsson)

Email discussion on XR capacity enhancement by October 19

-        Check points: October 14, October 19

R1-2210410         Moderator Summary#1 - Study on XR Specific Capacity Improvements               Moderator (Ericsson)

R1-2210411        Moderator Summary#2 - Study on XR Specific Capacity Improvements               Moderator (Ericsson)

From Oct 13th GTW session

Agreement:

To study whether/how the enhanced CG candidate techniques are necessary and beneficial for improving XR capacity, focus at least on the following techniques:

·        Dynamic indication of the unused CG PUSCH occasion(s) or resource(s) by the UE

·        Increase CG PUSCH transmission occasions in a duration

Conclusion

No further discussion in RAN1 for Rel-18 XR to extend the support of legacy single DCI scheduling multi-PDSCHs for FR2-2, to other SCS in FR1/FR2-1.

 

 

Decision: As per email decision posted on Oct 19th,

Conclusion

The capacity gain performance results in R1-2208661, R1-2209658 and R1-2209198 corresponding to enhancements based on multi-PDSCH scheduling by a single DCI are captured in XR SI TR.

 

Conclusion

Study on enhancement for CBG based HARQ-ACK feedback reporting is down-prioritized in RAN1 XR SI.

 

Conclusion

The following proposed enhancements techniques to improve XR capacity performance are down-prioritized in RAN1 XR SI:

·        (P3-5-3) Study on PHR enhancement based on XR traffic arrival periodicity or UL pose periodicity.

·        (P3-5-4) Study mechanism of packet dropping based on the PDB requirement, to avoid resource waste due to the out-of-date packets.

Agreement

·        For further study the mechanisms to enable HARQ retransmission of a TB on a different cell than the cell of the initial TB transmission for CA operation on TDD cells, consider at least the following:

o   Capacity performance evaluation results

o   Complexity analysis and RAN2 impact

Conclusion

·        Study of soft HARQ-ACK and Delta MCS in RAN1 XR SI for improving XR capacity is down-prioritized.

·        Note: The corresponding capacity gain performance results in R1-2210003, R1-2208377 and R1-2203607 are captured in XR SI TR.

Conclusion

·        Study on enhanced CQI based on CBG transmission, and study on enhanced CQI based on DMRS for improving XR capacity are down-prioritized in RAN1 XR SI.

·        Note: The corresponding capacity gain performance results in R1-2208402 and R1-2209536 are captured in XR SI TR.

 

R1-2210412        Moderator Summary#3 - Study on XR Specific Capacity Improvements               Moderator (Ericsson)

From Oct 19th GTW session

Conclusion

Study on Cooperative MIMO via DL interference probing based on SRS enhancement for improving XR capacity is down prioritized in RAN1 XR SI.

Note: The corresponding capacity gain performance results in R1-2208377 are captured in XR SI TR.

 

 

Decision: As per email decision posted on Oct 20th,

Conclusion

No consensus to continue study on differentiation of XR multiple flows based on CG enhancement in RAN1 XR SI.

 

Conclusion

No consensus to continue study of multi-bits SR mechanisms for capacity improvement of XR traffic in RAN1 XR SI.

 

 

Final summary in R1-2210413.


 RAN1#111

9.10   Study on XR enhancements for NR

Please refer to RP-220285 for detailed scope of the SI.

 

[111-R18-XR] – Huilin (Qualcomm)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

 

R1-2212408         Work Plan for Rel-18 SI on XR Enhancements for NR             Rapporteur (Nokia, Qualcomm)

 

From AI 5

R1-2210826        LS on XR and Media Services      SA2, vivo

R1-2212855        Draft reply LS on XR and Media Services vivo

R1-2212967        Draft reply LS on XR and Media Services vivo

Decision: The draft LS is endorsed. Final LS is approved in R1-2212994.

 

From Nov 18th session

Conclusion

From RAN1 perspective, the Rel-18 XR study item in RAN1 is completed.

 

Email discussion on the approval of XR TR from Nov 28 until Nov 29. Including approval of LS to RAN2.

·         R1-2212860, R1-2212936

·         Margarita/Huilin (Nokia/Qualcomm)

9.10.1     XR specific power saving techniques

R1-2210906        Discussion on XR-specific power saving techniques              Huawei, HiSilicon

R1-2210922         Discussion on power saving enhancements for XR     Ericsson

R1-2212518         Discussion on XR specific power saving enhancements            vivo       (rev of R1-2211024)

R1-2211174         UE Power saving techniques for XR              CATT

R1-2211246         Discussion on XR specific power saving techniques   Spreadtrum Communications

R1-2211341         Discussions on techniques for XR Power Saving        xiaomi

R1-2211389         Discussion on XR specific power saving techniques   Intel Corporation

R1-2211490         Discussion on XR specific power saving techniques   OPPO

R1-2211536         Discussion on XR specific power saving enhancement for NR China Telecom

R1-2211539         XR specific power saving techniques            TCL Communication Ltd.

R1-2211551         XR-specific power saving enhancements      Nokia, Nokia Shanghai Bell

R1-2211566         Discussion on XR-specific power saving techniques  ETRI

R1-2211624         Discussion on XR-specific power saving techniques  Sony

R1-2211653         Discussion on XR specific power saving techniques   Panasonic

R1-2211697         Discussion on XR-specific power saving techniques  CMCC

R1-2211752         Discussion on XR specific power saving techniques   NEC

R1-2211781         XR-specific power saving techniques            Lenovo

R1-2211826         On XR specific power saving techniques      Apple

R1-2211842         Discussion on XR specific power saving techniques   InterDigital, Inc.

R1-2212596         Evaluation on XR specific power saving techniques   ZTE, Sanechips   (rev of R1-2211905)

R1-2211920         Further Discussion on XR power saving       III

R1-2212000         Discussion on XR specific power saving techniques   NTT DOCOMO, INC.

R1-2212062         Considerations on Power Savings for XR      Samsung

R1-2212134         Power saving techniques for XR     Qualcomm Incorporated

R1-2212253         On XR specific power saving techniques      MediaTek Inc.

R1-2212305         Discussion on XR-specific power saving techniques  LG Electronics

R1-2212387         On XR-specific power saving techniques      Google Inc.

 

R1-2212698        Moderator Summary#1 on XR specific power saving techniques      Moderator (Qualcomm Incorporated)

From Nov 15th session

Conclusion

·        No consensus to support PDCCH monitoring resume if UE transmits NACK after PDCCH skipping starts

o   Nokia, CATT, ZTE, Intel expressed concerns on the benefit of the above proposal

·        No consensus to support PDCCH skipping duration enhancements by i) additional PDCCH skipping durations (>3), ii) skipping till the start of next potential data arrival

o   Applies at least for the case where CDRX is not configured

§  Ericsson, Nokia, ZTE expressed concerns on the benefit of the above proposal

·        No consensus to support additional active time by 1) UE extending DRX active time if UE does not receive XR data within current active time, 2) gNB using dynamic signaling such as a DCI to trigger additional On Duration if the data packet arrives after the On Duration expires

·        No consensus to support dynamic periodicity alignment between CDRX and XR traffic

 

R1-2212699        Moderator Summary#2 on XR specific power saving techniques      Moderator (Qualcomm Incorporated)

From Nov 17th session

Conclusion

There is no consensus on the following proposals in Table 1 for CDRX enhancements and Table 2 for PDCCH monitoring enhancements.

Table 1: CDRX enhancements

Proposal for CDRX enhancements

Proposal 2.2: support dynamic periodicity alignment between CDRX and XR traffic

Proposal 2.3-1: support additional active time by UE extending DRX active time if UE does not receive XR data within current active time

Proposal 2.3-2: support additional active time by gNB using dynamic signaling such as a DCI to trigger additional On Duration if the data packet arrives after the On Duration expires

Proposal 2.4: support non-uniform PMOs within CDRX On Duration

Proposal 2.5: support two-stage CDRX On Duration

Proposal 2.6-1: support early stopping of On-Duration timer by inactivity timer expiration

Proposal 2.6-2: support early stopping of On-Duration timer after a time window after the reception of XR data

Proposal 2.7: support multiple active CDRX configurations

Proposal 2.8: support dynamic grant enhancement with XR-specific pre-scheduling

Proposal 2.9: support SPS+DG with UE power saving scheme

Proposal 2.10: Support XR-specific plyaoutDelayForMediaStartup for XR UE power saving enhancement

 

Table 2: PDCCH monitoring adaptation enhancements

Proposals for PDCCH monitoring adaptation enhancements

Proposal 3.1: support PDCCH monitoring resume if UE transmits NACK after PDCCH skipping starts

Proposal 3.2-1: support PDCCH skipping duration enhancements by additional PDCCH skipping durations (>3)

Proposal 3.2-2: support PDCCH skipping duration enhancements by PDCCH skipping till the start of next potential data arrival

Proposal 3.3-1: support non-scheduling DCI based PDCCH skipping indication

Proposal 3.3-2: support continuous PDCCH skipping, i.e., UE continuously skips the PDCCH MOs until the DCI is successfully decoded at the time of packet arrival

Proposal 3.4: support an implicit SSSG at the start of drx-OnDuration and another SSSG applies when a PDCCH for data traffic is received, with search space set monitoring pattern aligned with DRX cycle

 

 

R1-2212700        Moderator Summary#3 on XR specific power saving techniques      Moderator (Qualcomm Incorporated)

Presented in Nov 18th session.

 

 

Final summary in R1-2212701.

9.10.22     XR-specific capacity enhancements techniques

R1-2210849         XR Capacity Evaluation and Enhancements FUTUREWEI

R1-2212650         Discussion on XR-specific capacity enhancements techniques Huawei, HiSilicon               (rev of R1-2210907)

R1-2210923         Discussion on capacity enhancements for XR              Ericsson

R1-2212595         Discussion on XR specific capacity enhancements     vivo       (rev of R1-2211025)

R1-2211175        NR enhancement for XR capacity improvement    CATT

R1-2211415         Discussion on XR specific capacity enhancement techniques   Intel Corporation

R1-2211491         Discussion on XR specific capacity enhancements techniques OPPO

R1-2211540         XR-specific capacity enhancements techniques           TCL Communication Ltd.

R1-2211552         XR-specific capacity enhancements Nokia, Nokia Shanghai Bell

R1-2211625         XR-specific capacity enhancements and evaluation results       Sony

R1-2211654         Discussion on XR capacity enhancement techniques  Panasonic

R1-2211698         Discussion on XR-specific capacity enhancements techniques CMCC

R1-2211782         XR-specific Capacity Enhancement Techniques         Lenovo

R1-2211827         On XR-specific capacity enhancements techniques     Apple

R1-2211843         Discussion on XR-specific capacity enhancements techniques InterDigital, Inc.

R1-2211906         XR specific capacity enhancements ZTE, Sanechips

R1-2212001         Discussion on XR specific capacity improvement enhancements            NTT DOCOMO, INC.

R1-2212063         Considerations on Capacity Improvements for XR      Samsung

R1-2212135         Capacity enhancement techniques for XR     Qualcomm Incorporated

R1-2212254         On XR specific capacity improvement enhancement  MediaTek Inc.

R1-2212275         Discussion on XR-specific capacity enhancements techniques KT Corp.

R1-2212306         Discussion on XR-specific capacity enhancement techniques   LG Electronics

R1-2212365         Discussion on XR-specific capacity enhancements     NEC

R1-2212386         On XR-specific capacity enhancements techniques     Google Inc.

 

R1-2212606        Moderator Summary#1 - Study on XR Specific Capacity Improvements               Moderator (Ericsson)

From Nov 15th session

 

R1-2212732        [Draft] TR 38.835 - TP for Capacity evaluation results        Rapporteur (Nokia)               (rev of R1-2212407)

Decision: The TPs for XR TR in R1-2212732 are endorsed in principle.

 

Conclusion

·        The capacity gain performance results in R1-2210907 (Huawei/HiSilicon) corresponding to enhancements based on UL delay aware scheduling are captured in XR SI TR.

Conclusion

·        The capacity gain performance results in R1-2211906 (ZTE/Sanechips) and R1-2211175 (CATT) corresponding to BSR enhancements are captured in XR SI TR.

Conclusion

·        The capacity gain performance results in R1-2211175 (CATT) corresponding to enhanced CG+DG scheme are captured in XR SI TR.

o   Note: SU-MIMO is used for baseline and MU-MIMO for the proposed enhancement.

Conclusion

·        The capacity gain performance results in R1-2211175 (CATT) corresponding to XR-specific playoutDelayForMediaStartup enhancement scheme are captured in XR SI TR.

 

Agreement:

Support dynamic indication of the unused CG PUSCH occasion(s) based on UCI (e.g., CG-UCI or a new UCI) by the UE.

 

Agreement:

Support multiple CG PUSCH transmission occasions in a period of a single CG PUSCH configuration.

 

Conclusion

No consensus on the following

·        Support dynamic indication of the unused CG PUSCH resource(s) based on UCI (e.g., CG-UCI or a new UCI) by the UE

 

R1-2212607        Moderator Summary#2 - Study on XR Specific Capacity Improvements               Moderator (Ericsson)

From Nov 17th session

Conclusion:

·        Deprioritize discussion on HARQ retransmission of a TB on a different cell than the cell of the initial TB transmission for CA operation on TDD cells in XR agenda.

Conclusion:

·        Deprioritize in RAN1, the study of XR-specific playoutDelayForMediaStartup for XR awareness scheduling to improve XR capacity enhancement.

Conclusion:

The capacity gain performance results in R1-2210907 and R1-2212254 corresponding to enhancements on RRM measurement are captured in XR SI TR.

 

Conclusion

No consensus on the following:

Enhancements on RRM to relax scheduling restriction for at least for intra-frequency RRM without MGs in FR2 and for inter-frequency RRM with MGs.

 

 

R1-2212608        Moderator Summary#3 - Study on XR Specific Capacity Improvements               Moderator (Ericsson)

From Nov 18th session

Agreement

The following TP for section 5.3.1 is endorsed in principle for TR 38.835:

The following enhancements for configured grant based transmission are recommended:

·        Multiple CG PUSCH transmission occasions in a period of a single CG PUSCH configuration;

·        Dynamic indication of unused CG PUSCH occasion(s) based on UCI (e.g., CG-UCI or a new UCI) by the UE.

The corresponding capacity performance evaluation results are available in Annex B.1.6.

The evaluation results for other proposed and studied capacity enhancement schemes are available in Annex B.1.

 

 

Final summary in R1-2212609.


 RAN1#112

9.10   XR Enhancements for NR

Please refer to RP-223502 for detailed scope of the WI.

 

[112-R18-XR] – Sorour (Ericsson)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

 

R1-2301626        Work Plan for Rel-18 WI on XR Enhancements for NR      Nokia, Qualcomm (Rapporteurs), Ericsson (RAN1 FL)

9.10.11     XR-specific capacity enhancements

R1-2300070         XR-specific capacity enhancements FUTUREWEI

R1-2300123         Discussion on CG enhancements for XR capacity       Huawei, HiSilicon

R1-2300137         Capacity Enhancements for XR       Ericsson

R1-2300235         Discussion on XR-specific capacity enhancements     Spreadtrum Communications

R1-2300291         Discussion on XR specific capacity enhancements     OPPO

R1-2300326         On XR-specific capacity enhancements techniques     Google Inc.

R1-2300374         Discussion on XR specific capacity enhancements     ZTE, Sanechips

R1-2300471         Discussion on XR specific capacity enhancements     vivo

R1-2300493         Discussion on XR-specific capacity enhancements     FGI

R1-2300552         Discussion on XR-specific capacity enhancements     xiaomi

R1-2300657         Design of Multiple CG Occasions   CATT

R1-2300739         XR-specific capacity enhancements Nokia, Nokia Shanghai Bell

R1-2300783         Discussion on XR-specific capacity enhancements     InterDigital Communications

R1-2300818         Discussion on XR-specific capacity enhancements     NEC

R1-2300839         XR-specific capacity enhancements techniques           TCL Communication Ltd.

R1-2300887         Considerations on XR-specific capacity enhancements             Sony

R1-2300965         Discussion on XR capacity enhancement techniques  Intel Corporation

R1-2301020         Discussion on XR-specific capacity enhancements     CMCC

R1-2301034         Discussion on XR-specific capacity enhancements     DENSO CORPORATION

R1-2301100         Discussion on XR capacity enhancement techniques  Panasonic

R1-2301111         Discussion on XR-specific capacity enhancements     LG Electronics

R1-2301207         XR-related CG Enhancements         Lenovo

R1-2301282         Capacity Improvements for XR       Samsung

R1-2301364         Discussion on XR-specific capacity enhancements     Apple

R1-2301431         Capacity Enhancement Techniques for XR   Qualcomm Incorporated

R1-2301511         Discussion on XR-specific capacity enhancements     NTT DOCOMO, INC.

R1-2301780         Discussion on XR capacity enhancements    MediaTek Inc.     (rev of R1-2301606)

 

R1-2301900        Moderator Summary#1 - XR Specific Capacity Improvements         Moderator (Ericsson)

From Tuesday session

Conclusion

For convenience in discussion, the term "multi-PUSCHs CG" refers to " a CG PUSCH configuration with multiple CG PUSCH transmission occasions within a period of the CG PUSCH configuration".

 

Agreement

·        Multi-PUSCHs CG is supported for Type-1 configured grant.

·        Multi-PUSCHs CG is supported for Type-2 configured grant.

Agreement

For determination of the time domain resource allocation of CG PUSCHs associated to a multi-PUSCHs CG, the following alternatives for further study:

FFS details, including related RRC parameters

 

Agreement

For the PUSCHs parameters in a multi-PUSCHs CG configuration, the configuration/indication parameters except MCS and FDRA of CG PUSCHs in a multi-PUSCHs CG configuration are the same

·        FFS: For MCS and FDRA, study further to decide whether/how to be different.

·        FFS: Applicability to type-1 and type-2

·        Note: TDRA and HP ID are not in this scope of the above statement.

Conclusion

RAN1 discusses to decide how to determine the HARQ process ID of CG PUSCHs of a multi-PUSCHs CG.

 

Agreement

For determination of HARQ process IDs associated to PUSCHs in multi-PUSCHs CG assuming one TB per PUSCH, consider the following alternatives:

Note: The case of one TB map to multiple PUSCHs is not considered here.

 

 

R1-2301901        Moderator Summary#2 - XR Specific Capacity Improvements         Moderator (Ericsson)

From Thursday session

Agreement

The physical channel that carries the UCI that provides information about unused CG PUSCH transmission occasions is CG PUSCH.

 

Agreement

Encoding and multiplexing for “the UCI that provides information about unused CG PUSCH transmission occasions” in a CG PUSCH applies encoding and multiplexing procedures for CG-UCI as baseline.

·        FFS on details

Agreement

Consider the following alternatives for “the UCI that provides information about unused CG PUSCH transmission occasions” for down-selection or revision

·        Alt. 1: “The UCI that provides information about unused CG PUSCH transmission occasions” is defined as a new UCI.

o   FFS on details

·        Alt. 2: “The UCI that provides information about unused CG PUSCH transmission occasions” is added as new field(s) to the CG-UCI.

o   FFS on details

·        Alt. 3: “The UCI that provides information about unused CG PUSCH transmission occasions” replaces/re-purposes some field(s) of the CG-UCI.

o   FFS on details

 

R1-2301902        Moderator Summary#3 - XR Specific Capacity Improvements         Moderator (Ericsson)

From Friday session

Agreement

For dynamic indication of unused CG PUSCH occasion(s) based on a UCI, the following options for further down-scoping with possible revision, are considered for the transmission occasion of the UCI:

Other options are not precluded. Proponent companies to provide details.

 

Agreement

For dynamic indication of unused CG PUSCH transmission occasion(s) based on a UCI, the following options for further down-scoping, are considered for the information provided by the UCI:

 

 

Final summary in R1-2301903.


 RAN1#112-bis-e

9.8       XR Enhancements for NR

Please refer to RP-230786 for detailed scope of the WI.

Including discussions on PDCCH monitoring resumption after UL NACK. Interested companies are to submit draft CR(s) to show the impacts of adding this functionality. These tdocs are to be submitted to agenda item 9.8.

 

R1-2303826         Work Plan for Rel-18 WI on XR Enhancements for NR            Nokia, Qualcomm (Rapporteurs), Ericsson (RAN1 FL)

 

R1-2302398         PDCCH monitoring resumption after UL NACK         Ericsson

R1-2302500         Draft CR on PDCCH monitoring resumption after NACK        vivo, MediaTek, Google, Qualcomm, Panasonic, Meta, Ericsson, China Unicom, Huawei, HiSilicon, Xiaomi, Apple, China Telecom

R1-2302676         PDCCH Skipping interaction with HARQ    CATT

R1-2302946         Discussion on PDCCH monitoring resumption after reporting NACK    ZTE, Sanechips

R1-2303312         Draft CR for Introducing PDCCH monitoring resumption after UL NACK               Nokia, Nokia Shanghai Bell

 

[112bis-e-R18-XR-01] – Sorour (Ericsson)

Email discussion on PDCCH monitoring resumption after UL NACK by April 21st

R1-2304041        Moderator Summary#1 - PDCCH monitoring resume after UL NACK               Moderator (Ericsson)

From April 18th GTW session

Proposal 1:

The following is supported: Resume PDCCH monitoring if UE transmits NACK after PDCCH skipping is started.

 

 

R1-2304042        Moderator Summary#2 - PDCCH monitoring resume after UL NACK               Moderator (Ericsson)

From April 24th GTW session

 

Outcome of discussion on PDCCH monitoring resume after UL NACK

In RAN1#112bis-e, text proposal alternatives to implement PDCCH monitoring resumption after UL NACK after PDCCH skipping is started were provided in R1-2304042 (by the moderator based on email discussions). The text proposal alternatives were to be discussed and finalized so that RAN1 can submit a converged text proposal to RAN. However, during the review process, CATT and Intel expressed sustained objections on the candidate TPs. They also expressed sustained objections on the support of this feature.

 

 

Final summary in R1-2304043.

9.8.11        XR-specific capacity enhancements

R1-2302317         XR-specific capacity enhancements FUTUREWEI

R1-2302346         Discussion on CG enhancements for XR capacity       Huawei, HiSilicon

R1-2302399         Capacity Enhancements for XR       Ericsson

R1-2302429         Discussions on XR-specific capacity enhancements   New H3C Technologies Co., Ltd.

R1-2302501         Discussion on XR specific capacity enhancements     vivo

R1-2302563         Discussion on XR specific capacity enhancements     OPPO

R1-2302615         Discussion on XR-specific capacity enhancements     Spreadtrum Communications

R1-2302718         Design of Multiple CG Occasions   CATT

R1-2302811         Discussion on XR specific capacity enhancement techniques   Intel Corporation

R1-2302836         XR-specific capacity enhancements techniques           TCL Communication Ltd.

R1-2302856         Discussion on XR-specific capacity enhancements     Sony

R1-2302879         On XR-specific capacity enhancements techniques     Google Inc.

R1-2302893         Discussion on XR capacity enhancement techniques  Panasonic

R1-2302947         Discussion on XR specific capacity enhancements     ZTE, Sanechips

R1-2302997         Discussion on XR-specific capacity enhancements     xiaomi

R1-2303023         Discussion on XR-specific capacity enhancements     InterDigital, Inc.

R1-2303143         Capacity improvements for XR       Samsung

R1-2303190         Discussion on XR specific capacity enhancements     CAICT

R1-2303249         Discussion on XR-specific capacity enhancements     CMCC

R1-2303311         XR-specific capacity enhancements Nokia, Nokia Shanghai Bell

R1-2303356         On XR capacity enhancements        MediaTek Inc.

R1-2303409         Discussion on XR-specific capacity enhancements     FGI

R1-2303428         Discussion on XR-specific capacity enhancements     LG Electronics

R1-2303460         Remaining issues on XR-specific capacity enhancements         Sharp

R1-2303498         XR-specific capacity enhancements Apple

R1-2303533         XR-related CG Enhancements         Lenovo

R1-2303605         Capacity Enhancement Techniques for XR   Qualcomm Incorporated

R1-2303672         Discussion on XR-specific capacity enhancements     NEC

R1-2303724         Discussion on XR-specific capacity enhancements     NTT DOCOMO, INC.

R1-2303827         Discussion on XR-specific capacity enhancements     DENSO CORPORATION

 

[112bis-e-R18-XR-02] – Sorour (Ericsson)

Email discussion on XR-specific capacity enhancements by April 26th

-        Check points: April 21, April 26

R1-2304044        Moderator Summary#1 - XR Specific Capacity Improvements         Moderator (Ericsson)

From April 18th GTW session

Agreement

For TDRA design for multi-CG PUSCH, prioritize Alt-A1, Alt-B, and Alt-C2 for further downscoping and/or modification from corresponding agreement in RAN1#112.

·        FFS: How to address TDD configuration issue

 

Agreement

For CG PUSCHs in a multi-PUSCHs CG configuration, MCS of the CG PUSCHs in the CG configuration are the same between different PUSCH occasions.

 

Agreement

For CG PUSCHs in a multi-PUSCHs CG configuration, FDRA of the CG PUSCHs in the CG configuration are the same between different PUSCH occasions.

 

 

R1-2304045        Moderator Summary#2 - XR Specific Capacity Improvements         Moderator (Ericsson)

From April 20th GTW session

Agreement

For dynamic indication of unused CG PUSCH transmission occasion(s) based on a UCI, the indicated “unused” CG PUSCH TO(s), if any, by the UCI in a CG PUSCH for a CG configuration

Note: FFSs and further details in corresponding agreement in RAN1#112 for the selected option are remained for further discussion

Note: Above corresponds to Option 2 (w.r.t. agreement in RAN1#112)

 

Agreement

 

Agreement

The UCI that provides information about unused CG PUSCH transmission occasions is defined as a “new UCI” (i.e. Alt. 1 of previous agreement).

 

Agreement

 

 

R1-2304046        Moderator Summary#3 - XR Specific Capacity Improvements         Moderator (Ericsson)

From April 24th GTW session

Agreement

The existing CG-UCI encoding and multiplexing procedures are reused for encoding the “UTO-UCI” in a configured grant PUSCH in absence or presence of other UCIs being multiplexed in the PUSCH, by applying the following adjustments:

 

 

R1-2304047        Moderator Summary#4 - XR Specific Capacity Improvements         Moderator (Ericsson)

From April 26th GTW session

Agreement

From RAN1 perspective, for determination of HARQ process Ids associated to PUSCHs in multi-PUSCHs CG assuming one TB per PUSCH:

 

Agreement

The UTO-UCI provides a bitmap where a bit corresponds to a TO within a time duration/range. The bit indicates whether the TO is “unused”.

·        FFS: Details including time duration/range

Note: The term “UTO-UCI” refers to the “UCI that provides information about unused CG PUSCH transmission occasions” for convenience.

 

 

Final summary in R1-2304048.